Update release policy page#688
Conversation
There was a problem hiding this comment.
The bootstrapping is always difficult. Given that, why don't we give an explicit example like 2026 and 2027 release plan, @HyukjinKwon and @cloud-fan ?
For example, I guessed like the following but it seems that this PR has a different timeline.
- 4.2.0 (The original plan): 2026 Summer + 18 months.
- 4.3.0 (LTS based on SPIP)
- 4.3.0 RC1 will start after 3 months from the release day of Apache Spark 4.2.0 in 2026.
- In 2027, Spark 5 will start as the annual release with the quarterly feature releases.
- Spark 5.0: 2027.1
- Spark 5.1: 2027.4
- Spark 5.2: 2027.7
- Spark 5.3: 2027.10 (LTS based on SPIP)
I just want to understand our plan of migration toward this SPIP. So, if there is an explicit example for 2026 and 2027. It would be perfect for me and all. The above is only one of personal understanding.
|
cc @peter-toth , too. |
|
I believe this is ready for another look. |
HyukjinKwon
force-pushed
the
faster-release-update
branch
from
8b76677 to
4163d81
Compare
|
Should be ready for a look. |
|
Thank you for updating, @HyukjinKwon . |
HyukjinKwon
force-pushed
the
faster-release-update
branch
from
4163d81 to
60abc46
Compare
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
+1, LGTM. Thank you, @HyukjinKwon !
There was a problem hiding this comment.
The wording here is a bit misleading. LTS is also annually, but it's 3 month after the latest feature release.
Strictly speaking, Feature release is also not 3 month cadency, as major release and LTS are not feature releases.
Maybe we can say it more general: we plan to ship a release every 3 months. We bump the major release version every 4 releases. The first release in the line is the major release, the last release in the line is LTS.
6 participants
This PR updates Release Policy page per SPIP: Accelerating Apache Spark Release Cadence.